EnigmA Amiga Run 1995 November/EnigmA AMIGA RUN 02 (1995)(G.R. Edizioni)(IT)[!][issue 1995-11][Skylink CD].iso/earcd/program/amos/amoslist.lzh/AMOSLIST/[e-mail]_Wed Sep 27 04:54:14 1995.msg

Internet Message Format | 1995-10-02 | 5KB

Received: from svcs1.digex.net (svcs1.digex.net [204.91.197.224]) by mail1.access.digex.net (8.6.12/8.6.12) with ESMTP id EAA23382;  for <[e-mail]> ; Wed, 27 Sep 1995 04:54:13 -0400
Received: (from daemon@localhost) by svcs1.digex.net (8.6.12/8.6.12) id BAA26010 for amos-out; Wed, 27 Sep 1995 01:18:11 -0400
Received: from mail1.access.digex.net (mail1.access.digex.net [205.197.247.2]) by svcs1.digex.net (8.6.12/8.6.12) with ESMTP id BAA26007 for <[e-mail]>; Wed, 27 Sep 1995 01:18:10 -0400
Received: from disperse.demon.co.uk (pong.demon.co.uk [158.152.1.64]) by mail1.access.digex.net (8.6.12/8.6.12) with SMTP id BAA10961;  for <[e-mail]> ; Wed, 27 Sep 1995 01:18:02 -0400
Received: by disperse.mail.demon.net id aa06926; 27 Sep 95 2:56 +0100
Received: from [158.152.1.72] by disperse.mail.demon.net id aa29573;
          23 Sep 95 10:15 +0100
Received: from westmead.demon.co.uk by post.mail.demon.net id aa05877;
          23 Sep 95 10:06 +0100
From: Mark Carter <[e-mail]>
Organization:  None Whatsoever
To: [e-mail]
Date:          Sat, 23 Sep 1995 10:06:56 +0000
Subject:       Re: Bits and Pieces
Priority: normal
X-mailer: Pegasus Mail/Windows (v1.22)
Message-ID:  <[e-mail]>
Status: RO
X-Status:

> Hi again!  Just found this message stuck here, I've been meaning to
> get back to it for ages!!
>
> > > > Has anyone found a way of using a joystick in place of a mouse in
> > > > conjunction with interface programs - I have tried several methods
> > > > and failed :-(  I want to be able to move my joystick so that the
> > > > mouse pointer moves (that bits easy) and then when I press fire over
> > > > a button I want the interface program to recognise that that button
> > > > has been clicked - any ideas?
>
> <bit bit about ZDIALOG cut out>

Yes, I've been using this one ever since it was included in amos :-||

> > > You could make the joystick move the mouse (say with AMAL to be
> >
> > Hmmn, can anyone confirm this?  I know the manual keeps on going on
> > about AMAL being much faster than their basic equivalents - but from
> > my own personal experience this is not true. I don't know.
>
> AMAL may not be any quicker, but it does mean you can make your
> routine for moving the mouse using the joystick, stick it in at the
> beginning and it'll run quite happily in the background.  Avoids
> having to constantly call a procedure or insert extra commands
> everywhere.  Can just be controlled with AMAL UNFREEZE and AMAL
> FREEZE.
>
> It doesn't sound as if speed is that vital for this particular
> example?

That's true - its just a matter of taste :-6

> > > quick) and then when the joystick button is pressed and the mouse is
> > > over the button it DIALOG UPDATEs the button to its pressed state and
> > > when you release it it DIALOG UPDATEs it back and continues.
> > >
> > > Is this any help?
> >
> > Thanks for your help.
> >
> > I remember trying DIALOG UPDATE before but then I rejected it and I
> > cant remember why.  One reason may be the inability of the function
> > to cope with radio buttons (but I dont mind this TOO much).
>
> Yeah, I'm sure it doesn't work with these as radio buttons are all
> assigned the same button number, aren't they?  (major pain!)
>
> > Another reason may have been that I thought that the command does not
> > execute the "Button Change" code, but instead just the first bit of code
> > which usually draws the button in whatever state its currently in -
> > understand...?
>
> I'm sure it does... oh, then again, all my interface code has used
> the first bit which then is dependent on the ButtonPosition, I think.
>  What have you got in your button change bit?  Anything that can just
> be emulated in normal Amos?
>
> > However, today I found out that this clearly is not the case.
> > Is it true that calling the DIALOG UPDATE (1,BUT,1-RDIALOG(1,BUT))
> > command when the fire button is pressed and then the same command
> > when the fire button is released will EXACTLY emulate the clcik of a
> > mouse button on a button which features the BR0 command so that it
> > returns to its original position.
>
> Not sure.  I would think it should, but I could be wrong.
>

I wonder....
If you have a button which automatically returns to its default
status when you release the mouse button (using BR0;), would you get
the same result if you try to emulate this in amos by calling the
Dialog Update (1,BUT,1) followed by Dialog Update(1,BUT,0). (phew,
that was a long sentance!)  I've got a feeling that the Button Change
code would be executed twice - and this would be wrong.

I'm gonna test this out today - once and for all.

>
> --
> Sorry it took me so long to reply, I think I first read it when I was
> drunk and there was one bit I couldn't get my head around!

Well, sorry`s not good enough ;-)

> Sorry if it's come too late!

You`re ok.

> How are you getting on with it?

95% done - but still a long way to go!

Slow going at the moment - motivation is the problem.  I've done all
the interesting bits - its mainly gameplay left.


Cheers,

Mark

Mark Carter
e-mail: [e-mail],   [e-mail]